Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a47f74ddf671c72cf06d03a2bbe4b15412a61ddcf132c6ee1b0b1029447606fe

Tx prefix hash: da00b9a316a7c32edf9b2e3d1e4118593644bd24112580d58d0f508f7c37d4bd
Tx public key: 872abf3736d7227b116d5c7b1f72903d269fd6c04bcf0e30626de9bfdff76230
Timestamp: 1711220015 Timestamp [UCT]: 2024-03-23 18:53:35 Age [y:d:h:m:s]: 01:227:06:57:18
Block: 984786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421095 RingCT/type: yes/0
Extra: 01872abf3736d7227b116d5c7b1f72903d269fd6c04bcf0e30626de9bfdff762300211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdfedf555cd18a4a0bc6be122c107833ccc754796171b40c067f0566b3617d22 0.600000000000 1444959 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": 984796, "vin": [ { "gen": { "height": 984786 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdfedf555cd18a4a0bc6be122c107833ccc754796171b40c067f0566b3617d22" } } ], "extra": [ 1, 135, 42, 191, 55, 54, 215, 34, 123, 17, 109, 92, 123, 31, 114, 144, 61, 38, 159, 214, 192, 75, 207, 14, 48, 98, 109, 233, 191, 223, 247, 98, 48, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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