Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2955f865622370a3ab9011a33fe946a14d98fc4c7a8ff354f8263191ef1de40a

Tx prefix hash: bb63fd538f2f702d2db06ad4c2393cecf3043271958829932b2c32172977b697
Tx public key: 1531b00c7ba5ea5876e1934bbfe290ca31b69fd6183ad40e48b5b0ed323eca4f
Timestamp: 1719441375 Timestamp [UCT]: 2024-06-26 22:36:15 Age [y:d:h:m:s]: 00:291:17:44:33
Block: 1052918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208475 RingCT/type: yes/0
Extra: 011531b00c7ba5ea5876e1934bbfe290ca31b69fd6183ad40e48b5b0ed323eca4f02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b8c6e91e945fb435b969acb4ce1f01cbaedc0a5b91cd4e6eb3cf9fd52e1dc4b 0.600000000000 1523263 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": 1052928, "vin": [ { "gen": { "height": 1052918 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b8c6e91e945fb435b969acb4ce1f01cbaedc0a5b91cd4e6eb3cf9fd52e1dc4b" } } ], "extra": [ 1, 21, 49, 176, 12, 123, 165, 234, 88, 118, 225, 147, 75, 191, 226, 144, 202, 49, 182, 159, 214, 24, 58, 212, 14, 72, 181, 176, 237, 50, 62, 202, 79, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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