Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 548524148f64e2d0ed47af1e1f26c786fa26713f6bdafd34cbc6fef0710f7247

Tx prefix hash: b14520fd71ac3b86099270b97eb7d89f809377a228561b1a236a6db020c88c03
Tx public key: bf26b288d325cbf8c8218161e763cde7fe7e9e6b703960d7d290cd839a7be4ce
Timestamp: 1722131279 Timestamp [UCT]: 2024-07-28 01:47:59 Age [y:d:h:m:s]: 00:245:15:25:45
Block: 1075218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175463 RingCT/type: yes/0
Extra: 01bf26b288d325cbf8c8218161e763cde7fe7e9e6b703960d7d290cd839a7be4ce02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a3cca856635a0f82e363faf1e31e457ab096b177f7077273dc90e193e4b977d 0.600000000000 1547741 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": 1075228, "vin": [ { "gen": { "height": 1075218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a3cca856635a0f82e363faf1e31e457ab096b177f7077273dc90e193e4b977d" } } ], "extra": [ 1, 191, 38, 178, 136, 211, 37, 203, 248, 200, 33, 129, 97, 231, 99, 205, 231, 254, 126, 158, 107, 112, 57, 96, 215, 210, 144, 205, 131, 154, 123, 228, 206, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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