Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4899869bf181948e83a03dcc6ce9edfe444658ba39ce5e15b33b062a4e1f980

Tx prefix hash: 8fdb213746c821c500182f75489bcf23ead0044b09b94714314f0ba7ebb64853
Tx public key: 1cea06ce6eb7c418c946ba1c68f6a189ab62cbaabf2c3e72efd7ce4cbe6b2075
Timestamp: 1736974122 Timestamp [UCT]: 2025-01-15 20:48:42 Age [y:d:h:m:s]: 00:059:12:00:56
Block: 1198126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42319 RingCT/type: yes/0
Extra: 011cea06ce6eb7c418c946ba1c68f6a189ab62cbaabf2c3e72efd7ce4cbe6b20750211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 769bfe8f0a2115c08363b9075e2af56bc54e2aefd4bce23eb8ec0f0b98e0a2bd 0.600000000000 1684745 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": 1198136, "vin": [ { "gen": { "height": 1198126 } } ], "vout": [ { "amount": 600000000, "target": { "key": "769bfe8f0a2115c08363b9075e2af56bc54e2aefd4bce23eb8ec0f0b98e0a2bd" } } ], "extra": [ 1, 28, 234, 6, 206, 110, 183, 196, 24, 201, 70, 186, 28, 104, 246, 161, 137, 171, 98, 203, 170, 191, 44, 62, 114, 239, 215, 206, 76, 190, 107, 32, 117, 2, 17, 0, 0, 0, 3, 31, 10, 83, 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