Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 289f1dca0aad6d1995898d0ccd6757ca64b72a30c2332458955c2ef05783bfb1

Tx prefix hash: 5f6cb888dcc5e56e12dabab7f4bc86e93a2b6aa04e35032a62d934096ca727f2
Tx public key: fba6e09f698df83915d1ebfb329e8e3574f64fe6eac402b03865cd7bc6cddd84
Timestamp: 1734605050 Timestamp [UCT]: 2024-12-19 10:44:10 Age [y:d:h:m:s]: 00:105:10:07:19
Block: 1178544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75112 RingCT/type: yes/0
Extra: 01fba6e09f698df83915d1ebfb329e8e3574f64fe6eac402b03865cd7bc6cddd84021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e8a5ce9df774ef69caf54243121f02f253d97da7374a80c8ba21dec240ad5d4 0.600000000000 1664931 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1178554, "vin": [ { "gen": { "height": 1178544 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e8a5ce9df774ef69caf54243121f02f253d97da7374a80c8ba21dec240ad5d4" } } ], "extra": [ 1, 251, 166, 224, 159, 105, 141, 248, 57, 21, 209, 235, 251, 50, 158, 142, 53, 116, 246, 79, 230, 234, 196, 2, 176, 56, 101, 205, 123, 198, 205, 221, 132, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8