Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41b39ac82616fe7985c4ade69e44771c2289cfacbe942a98740401650f9207e2

Tx prefix hash: 974c7f9671fd0f092873c266f01ab1a4b45aa714074b0f46a76fc6cfc5d2e62a
Tx public key: 40359c0cf23e86a8f15394ea69d2d3c76c761a69f07ad35114d12681b3e24e96
Timestamp: 1715018553 Timestamp [UCT]: 2024-05-06 18:02:33 Age [y:d:h:m:s]: 00:209:14:43:08
Block: 1016263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150041 RingCT/type: yes/0
Extra: 0140359c0cf23e86a8f15394ea69d2d3c76c761a69f07ad35114d12681b3e24e960211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 696f02800e1a03c49eee286aa2956058a718c40b50fb340e03eef7a528f75243 0.600000000000 1479794 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": 1016273, "vin": [ { "gen": { "height": 1016263 } } ], "vout": [ { "amount": 600000000, "target": { "key": "696f02800e1a03c49eee286aa2956058a718c40b50fb340e03eef7a528f75243" } } ], "extra": [ 1, 64, 53, 156, 12, 242, 62, 134, 168, 241, 83, 148, 234, 105, 210, 211, 199, 108, 118, 26, 105, 240, 122, 211, 81, 20, 209, 38, 129, 179, 226, 78, 150, 2, 17, 0, 0, 0, 3, 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