Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d7a76fce984df5aafdb1d4092dddce3d720fa9ae9c72e87db672f21d38f5abb

Tx prefix hash: 0972427e8757b7dd58f96f9651b5dd321c5002bba09c08295e88e2fbd7cabbd7
Tx public key: 19977b9957883dfcd32dc6e89d2a6589aec2a9cfab9401a49b434fa6788be875
Timestamp: 1672722177 Timestamp [UCT]: 2023-01-03 05:02:57 Age [y:d:h:m:s]: 02:110:09:48:29
Block: 666462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 600602 RingCT/type: yes/0
Extra: 0119977b9957883dfcd32dc6e89d2a6589aec2a9cfab9401a49b434fa6788be87502110000000252542ceb000000000000000000

1 output(s) for total of 3.799572143000 dcy

stealth address amount amount idx
00: 9a4158de2d8db7c9ae3c119c5957a14f364185ae3f671875bba8235c577a0f7e 3.799572143000 1107573 of 0

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": 666472, "vin": [ { "gen": { "height": 666462 } } ], "vout": [ { "amount": 3799572143, "target": { "key": "9a4158de2d8db7c9ae3c119c5957a14f364185ae3f671875bba8235c577a0f7e" } } ], "extra": [ 1, 25, 151, 123, 153, 87, 136, 61, 252, 211, 45, 198, 232, 157, 42, 101, 137, 174, 194, 169, 207, 171, 148, 1, 164, 155, 67, 79, 166, 120, 139, 232, 117, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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