Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bd957da35e6cb3d212134a216b9f1e670969a030f80b3af50a0dd5ccb647b94

Tx prefix hash: 7dca7f1e11412b70c03c78ab408f59beb84a9d4188ad0bc0cc0cecc0ae03d281
Tx public key: eaa03054218a51fefdee74a8f199aafd153f27b6c4452b586d7bc70b4bd9f8c6
Timestamp: 1645362362 Timestamp [UCT]: 2022-02-20 13:06:02 Age [y:d:h:m:s]: 03:085:09:14:28
Block: 442645 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 841091 RingCT/type: yes/0
Extra: 01eaa03054218a51fefdee74a8f199aafd153f27b6c4452b586d7bc70b4bd9f8c60211000000044a0f5013000000000000000000

1 output(s) for total of 20.957219103000 dcy

stealth address amount amount idx
00: 6b63a6d2c9a0aaad553a0e3d8b7ff69ab839c5deefa6f0c303c51844492cba16 20.957219103000 855480 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": 442655, "vin": [ { "gen": { "height": 442645 } } ], "vout": [ { "amount": 20957219103, "target": { "key": "6b63a6d2c9a0aaad553a0e3d8b7ff69ab839c5deefa6f0c303c51844492cba16" } } ], "extra": [ 1, 234, 160, 48, 84, 33, 138, 81, 254, 253, 238, 116, 168, 241, 153, 170, 253, 21, 63, 39, 182, 196, 69, 43, 88, 109, 123, 199, 11, 75, 217, 248, 198, 2, 17, 0, 0, 0, 4, 74, 15, 80, 19, 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