Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 322c60a9023dfb1faef142885d911261368ab80f72d2bd011cdc9b24bccb0e64

Tx prefix hash: be1b479343dbbcd8503dd5651e8e8ec0cc481df05fd8e2c715d58577170641d0
Tx public key: 5bd054791b0eb19a0792553464f29eeea76528681fee1eec8a4861fddd1a057f
Timestamp: 1726864717 Timestamp [UCT]: 2024-09-20 20:38:37 Age [y:d:h:m:s]: 00:268:04:53:15
Block: 1114470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191447 RingCT/type: yes/0
Extra: 015bd054791b0eb19a0792553464f29eeea76528681fee1eec8a4861fddd1a057f021100000001bdafe9cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0d9f491279aef74db8dddd6140871910a3cceb1b7bc7d7f36dc2c8c9e5e0f98 0.600000000000 1594271 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": 1114480, "vin": [ { "gen": { "height": 1114470 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0d9f491279aef74db8dddd6140871910a3cceb1b7bc7d7f36dc2c8c9e5e0f98" } } ], "extra": [ 1, 91, 208, 84, 121, 27, 14, 177, 154, 7, 146, 85, 52, 100, 242, 158, 238, 167, 101, 40, 104, 31, 238, 30, 236, 138, 72, 97, 253, 221, 26, 5, 127, 2, 17, 0, 0, 0, 1, 189, 175, 233, 204, 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