Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1bafc1c204e7eca101fa54b61bf8e309e152bbbf09c0d9a7825d70a06d85a42

Tx prefix hash: b3ad4488090ce4ca9c485269cdd3689b7e90b772b4e2e547e10bccce25501c0b
Tx public key: 0d8dfff1f96f75903a43ede1dbe42b158f69ca81e14fea7595bcb2cfcc2ccd48
Timestamp: 1702295297 Timestamp [UCT]: 2023-12-11 11:48:17 Age [y:d:h:m:s]: 01:343:00:09:50
Block: 910774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 504029 RingCT/type: yes/0
Extra: 010d8dfff1f96f75903a43ede1dbe42b158f69ca81e14fea7595bcb2cfcc2ccd48021100000002faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4f72c0964c9f6c8422ad18e9446c6fb86cc5b5817634431b679284c88ef5ed7 0.600000000000 1367941 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": 910784, "vin": [ { "gen": { "height": 910774 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4f72c0964c9f6c8422ad18e9446c6fb86cc5b5817634431b679284c88ef5ed7" } } ], "extra": [ 1, 13, 141, 255, 241, 249, 111, 117, 144, 58, 67, 237, 225, 219, 228, 43, 21, 143, 105, 202, 129, 225, 79, 234, 117, 149, 188, 178, 207, 204, 44, 205, 72, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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