Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 669f9e9d5d7b3d3374fcfd4410dda96062ed7d54c5544a5aee80062d55f753ea

Tx prefix hash: 56fbe08cd63c9eb34202fef62112a93f3059f5eca9e024fd49fc6d7b09bdf1ba
Tx public key: 2d9136c424b4e6b5aa4dd0af273ce38081f4ef808ab21a546d84be813ec2543f
Timestamp: 1727243466 Timestamp [UCT]: 2024-09-25 05:51:06 Age [y:d:h:m:s]: 00:060:12:33:25
Block: 1117612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43248 RingCT/type: yes/0
Extra: 012d9136c424b4e6b5aa4dd0af273ce38081f4ef808ab21a546d84be813ec2543f02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d7adf8712866b984b36aff47af1e1fd276a622fc1b776efb983b306a7ad06fa 0.600000000000 1598511 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": 1117622, "vin": [ { "gen": { "height": 1117612 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d7adf8712866b984b36aff47af1e1fd276a622fc1b776efb983b306a7ad06fa" } } ], "extra": [ 1, 45, 145, 54, 196, 36, 180, 230, 181, 170, 77, 208, 175, 39, 60, 227, 128, 129, 244, 239, 128, 138, 178, 26, 84, 109, 132, 190, 129, 62, 194, 84, 63, 2, 17, 0, 0, 0, 3, 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