Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0eeb2c1a72dbb5b879745e64d28611178bfa9c99a34175a546ac0d284ae57df2

Tx prefix hash: d784a37cbce75c299f79d2b5021d70403a8df3f64a5072bdfe6838e8c69172c2
Tx public key: 30c440a2ce86401df7859ebbf52ab927a57171ae35be4a95ee4c8d382a2dfa23
Timestamp: 1731112196 Timestamp [UCT]: 2024-11-09 00:29:56 Age [y:d:h:m:s]: 00:073:23:31:17
Block: 1149602 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52877 RingCT/type: yes/0
Extra: 0130c440a2ce86401df7859ebbf52ab927a57171ae35be4a95ee4c8d382a2dfa2302110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f53474769f7cf8e4b5b02f6ec370b242532af581e772eaa9988dce996a447888 0.600000000000 1634713 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": 1149612, "vin": [ { "gen": { "height": 1149602 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f53474769f7cf8e4b5b02f6ec370b242532af581e772eaa9988dce996a447888" } } ], "extra": [ 1, 48, 196, 64, 162, 206, 134, 64, 29, 247, 133, 158, 187, 245, 42, 185, 39, 165, 113, 113, 174, 53, 190, 74, 149, 238, 76, 141, 56, 42, 45, 250, 35, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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