Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d0aacc3c1872f18ea1adc36aa940b484257148f1a8acd113f22374994a180e3

Tx prefix hash: 196ebc9a683fbed7a13319657f23ae1616bd249318b9bc1f69b936de5d6e4b59
Tx public key: cfe14ab7985a94ca663ea3f64bcfb5f6074cc6812d9c129e796526c1438ea2c9
Timestamp: 1711051201 Timestamp [UCT]: 2024-03-21 20:00:01 Age [y:d:h:m:s]: 01:000:23:08:29
Block: 983385 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261647 RingCT/type: yes/0
Extra: 01cfe14ab7985a94ca663ea3f64bcfb5f6074cc6812d9c129e796526c1438ea2c902110000000f59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2dabbba11ec664d6c1938f5f65f960ecaead7d921d4029dbc93a6817aa7b3682 0.600000000000 1443512 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": 983395, "vin": [ { "gen": { "height": 983385 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2dabbba11ec664d6c1938f5f65f960ecaead7d921d4029dbc93a6817aa7b3682" } } ], "extra": [ 1, 207, 225, 74, 183, 152, 90, 148, 202, 102, 62, 163, 246, 75, 207, 181, 246, 7, 76, 198, 129, 45, 156, 18, 158, 121, 101, 38, 193, 67, 142, 162, 201, 2, 17, 0, 0, 0, 15, 89, 218, 211, 245, 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