Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e06469898b84f62830294c2214150731cc4e17a08ea53ef11122b9cf0e27e6a

Tx prefix hash: b15ad56a27b9d1afb88777483e98f05ea9073eb566d79ea26b4abbee0e115eb6
Tx public key: 893f1ed56f8adc0a123a3a4250e84418ece0ab74e5b707850f6b4c69066d4732
Timestamp: 1582262757 Timestamp [UCT]: 2020-02-21 05:25:57 Age [y:d:h:m:s]: 04:355:19:09:11
Block: 69317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1146545 RingCT/type: yes/0
Extra: 01893f1ed56f8adc0a123a3a4250e84418ece0ab74e5b707850f6b4c69066d47320211000000044ac5aa02000000000000000000

1 output(s) for total of 361.680262164000 dcy

stealth address amount amount idx
00: b11157ae6d97321166886b1cf6acb34dcb3e4551e02a812774454bf1648ad6a6 361.680262164000 127831 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": 69327, "vin": [ { "gen": { "height": 69317 } } ], "vout": [ { "amount": 361680262164, "target": { "key": "b11157ae6d97321166886b1cf6acb34dcb3e4551e02a812774454bf1648ad6a6" } } ], "extra": [ 1, 137, 63, 30, 213, 111, 138, 220, 10, 18, 58, 58, 66, 80, 232, 68, 24, 236, 224, 171, 116, 229, 183, 7, 133, 15, 107, 76, 105, 6, 109, 71, 50, 2, 17, 0, 0, 0, 4, 74, 197, 170, 2, 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