Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4c1c454f97990c8bf35de0066446a2b0e4aabfaa564cf572287ad3c5b20dcc3

Tx prefix hash: 0f979ad978b182d498b137bd025159279b039350c83099575b60c1698abfdcaa
Tx public key: 3a4fb3083feee9eed668f8e1d78a4b3913d780c74af1814ce765d592c6a475b2
Timestamp: 1732520247 Timestamp [UTC]: 2024-11-25 07:37:27 Age [y:d:h:m:s]: 01:359:12:54:24
Block: 1161255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 520887 RingCT/type: yes/0
Extra: 013a4fb3083feee9eed668f8e1d78a4b3913d780c74af1814ce765d592c6a475b20211000000041f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2c96e111272e20bf489464a3ed3cdb69f4ad1b94aa108cdb7bde01a2a5ef7a94 0.000600000000 1646906 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 dinastycoin-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": 1161265, "vin": [ { "gen": { "height": 1161255 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c96e111272e20bf489464a3ed3cdb69f4ad1b94aa108cdb7bde01a2a5ef7a94" } } ], "extra": [ 1, 58, 79, 179, 8, 63, 238, 233, 238, 214, 104, 248, 225, 215, 138, 75, 57, 19, 215, 128, 199, 74, 241, 129, 76, 231, 101, 213, 146, 198, 164, 117, 178, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: